System and method for accessing a multi-line gateway using cordless telephony terminals

ABSTRACT

According to the present invention, simultaneous call-handling and data transfer is achieved between a terminal and a multi-line gateway in a cordless telephony environment. Multiple logical channels are established and used as signaling resources for calls on the multiple lines, and also for data transfers between the gateway and terminal. As a result, terminals can handle multiple calls on different lines and at the same time access data stored at the gateway. According to a first aspect of the present invention, two or more logical channels are established over an asynchronous channel between a terminal and a gateway. These logical channels are assigned to calls that are set-up between the terminal and gateway. When used as a signaling resource, the logical channels allow the terminal to distinguish between signaling information for multiple simultaneous calls. The calls are associated with another speech or data channel that will bear the voice signal, referred to herein as a bearer channel. According to a second aspect of the present invention, a logical channel is also established over an asynchronous channel to handle data transfers between the gateway and terminal. Using this logical channel, the terminal can access data stored at the gateway without disrupting any ongoing calls.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.09/919,670 filed Jul. 31, 2001 now U.S. Pat. No. 6,973,058.

BACKGROUND

1. Field of the Invention

The present invention relates generally to wireless communications, andmore particularly to a system and method for accessing a multi-linegateway using cordless telephony terminals.

2. Discussion of the Related Art

In today's electronically interconnected world, the normal complement ofelectronic equipment in the home or business includes devices that areconnected to one another in different ways. For example, many desktopcomputer systems have a central processing unit (CPU) connected to amouse, a keyboard, a printer and so on. A personal digital assistant(PDA) will normally connect to the computer with a cable and a dockingcradle. A television may be connected to a VCR and a cable box, with aremote control for all three components. A cordless phone connects toits base unit with radio waves, and it may have a headset that connectsto the phone with a wire. In a stereo system, a CD player, tape playerand record player connect to a receiver, which connects to speakers.These connections can be difficult to install and maintain, particularlyfor the lay user.

Alternatives to these conventional approaches to connectivity have beenproposed. Bluetooth™ (BT) is a computing and telecommunications industryspecification for connectivity that is both wireless and automatic, asdescribed in The Specification of the Bluetooth System, Version 1.1,Feb. 22, 2001, (“the BT specification”), which is incorporated herein byreference. BT allows any sort of electronic equipment—from computers andcell phones to keyboards and headphones—to make its own connections,without wires, cables or any direct action from a user. Because BTconnections are wireless, offices can be designed without regard tocable placement and users can travel with portable devices withouthaving to worry about carrying a multitude of cables. These connectionscan be established automatically, where BT devices find one another andform a connection without any user input at all.

BT requires that a low-cost microchip transceiver be included in eachdevice. The BT microchip transceiver communicates on a frequency of 2.45GHz, which has been set aside by international agreement for the use ofindustrial, scientific and medical devices (ISM). In addition to data,up to three voice channels are available. Each BT device has a unique48-bit device address from the Institute of Electrical and ElectronicsEngineers 802 standard. Connections can be point-to-point ormulti-point. Data can be exchanged at a rate of 1 megabit per second (upto 2 Mbps in the second generation of the technology).

A number of common consumer devices also take advantage of the sameradio frequency (RF) band. Baby monitors, garage-door openers and somecordless phones all make use of frequencies in the ISM band. The BTdesign employs various techniques to reduce interference between thesedevices and BT transmissions. For example, BT avoids interfering withother systems by sending out relatively weak signals of 1 milliwatt. Bycomparison, some cell phones can transmit a signal of 3 watts. The lowpower limits the range of a BT device to about 10 meters, therebyreducing the probability of interference with other devices.

BT also employs a spread-spectrum frequency hopping scheme to furtherreduce interference and increase capacity. BT devices use 79 randomlychosen frequencies within a designated range, changing from one toanother on a regular basis 1,600 times every second. The randomfrequency hopping pattern makes it unlikely that two BT transmitterswill be on the same frequency at the same time, thus reducing theprobably of BT devices interfering with one another. This technique alsominimizes the risk that other non-BT devices such as portable phones orbaby monitors will disrupt BT devices since any interference on aparticular frequency will last only a fraction of a second.

When BT devices come within range of one another, an electronicconversation takes place to determine whether they have data to share orwhether one needs to control he other. Once the conversation hasoccurred, the devices form a “piconet”. A piconet ay link deviceslocated throughout a room, such as a home entertainment system, ordevices much closer together such as a mobile phone on a belt-clip and aheadset, or a computer, mouse, and printer. Once a piconet isestablished, the connected devices randomly hop frequencies in unison tocommunicate with one another and avoid other piconets that may beoperating nearby.

One device acts as the master of the piconet, whereas the other unit(s)acts as slave(s). Up to seven slaves can be active in a single piconet.The slaves synchronize to the master's timing, and access to the channelis controlled by the master. The channel is represented by apseudo-random hopping sequence hopping through the 79 RF channels. Thehopping sequence is unique for each piconet and is determined by the BTdevice address of the master, the phase in the hopping sequence isdetermined by the BT clock of the master. The channel is divided intotime slots where each slot corresponds to an RF hop frequency.Consecutive hops correspond to different RF hop frequencies. The nominalhop rate is 1,600 hops/second. All BT devices participating in thepiconet are time- and hop-synchronized to the channel.

Between master and slave(s), different types of links can beestablished. Two link types have been defined in the BT specifications:Synchronous Connection-Oriented (SCO) links, and AsynchronousConnection-Less (ACL) links. The SCO link is a point-to-point linkbetween a master and a single slave in the piconet. SCO links supportreal-time voice traffic using reserved bandwidth. The ACL link, bycomparison, is a point-to-multipoint link between the master and all theslaves participating on the piconet. In the slots not reserved for SCOlinks, the master can exchange packets with any slave on a per-slotbasis. The ACL link provides a packet-switched connection between themaster and all active slaves participating in the piconet.

Data on the piconet channel is conveyed in packets. Each packet consistsof three entities: the access code, the header, and the payload. Theaccess code and header are of fixed size: 72 bits and 54 bitsrespectively. The payload can range from zero to a maximum of 2745 bits.Packets may include the access code only, the access code header, or theaccess code header payload. In an ACL link, the master can eitherbroadcast packets to every slave in the piconet, or send packets to aparticular slave. ACL packets not addressed to a specific slave areconsidered as broadcast packets and are read by all the slaves. In thereverse direction, the master controls slave access to the channel.

As mentioned above, BT wireless techniques can be applied to a number ofenvironments. One such environment is cordless telephony. The CordlessTelephony Profile (CTP) portion of the BT specification, for example,describes a “3-in-1 phone” wherein an extra BT mode of operation isprovided to cellular phones. The 3-in-1 phone uses this BT mode as ashort-range bearer for accessing fixed network telephony services via abase station. The CTP describes various protocols for handling voice anddata transmissions between the base station, referred to in thespecification as a gateway, and a small number (maximum 7) of terminals.The gateway provides access to an external network, such as a publicswitched telephone network (PSTN). However, the techniques described inthe CTP can also be applied generally for wireless telephony in aresidential or small office environment, such as for cordless-onlytelephony or cordless telephony services in a personal computer (PC).

The CTP covers various scenarios, such as connecting to the gateway sothat incoming calls can be routed to the terminal and outgoing calls canbe originated, making a call from a terminal to a user on the externalnetwork, receiving a call from the external network, and making directcalls between two terminals. The CTP describes the gateway having asingle line connecting the gateway to the external network. Proceduresare described for handling calls received on this single line. Thissimple gateway will provide sufficient functionality for manyenvironments, such as for personal use in a home having a single phoneline.

However, many environments require that gateways support multiple linescoming from the external network. In this scenario, the terminals andgateway should be able to handle simultaneous calls on multiple lines.The CTP does not provide for this multi-line support. This limitationresults, at least in part, from the terminal's inability to distinguishsignaling information associated with calls that are occurringsimultaneously. Signaling information is transmitted as packets of dataAs defined in the BT specification, these packets do not contain a fieldfor identifying a particular call with which the packet is associated.This does not pose a problem when handling at most a single call at anygiven time, because the terminal assumes that all signaling informationis associated with the single call. Problems arise, however, whenpackets associated with simultaneous calls arrive at the terminal. Thepackets do not identify themselves with a particular call, and the CTPdoes not describe using any other mechanism for making this association.The terminal is therefore unable to handle the signaling associated withmultiple calls.

Furthermore, the CTP does not describe how terminals might access datastored at the gateway, nor does the CTP describe how data can beaccessed while simultaneously handling a call. In many scenarios, dataof interest to users could be stored by the gateway, such as phone bookdata, directories, and lists of phones calls made or received. Makingthis information available at the terminal requires that the stored databe transferred from the gateway to the terminal. The CTP does notdescribe procedures for accomplishing this transfer. There also could besituations where the user might wish to access this information during acall. For example, a user during a phone call might want to provide aphone number to another party on the call. It would be helpful if theuser could access conveniently the stored phone book data using theterminal, and then read the desired number to the other party. The CTPdoes not describe how to access data while simultaneously handling aphone call.

What is needed therefore is an improved system and method for supportingcalls on multiple lines in a cordless telephony environment. Further,there is also a need for an improved system and method for accessingdata stored at the gateway, particularly where the access occurs duringa call.

SUMMARY OF THE INVENTION

The present invention satisfies this need by providing a system andmethod for simultaneous call-handling and data transfer between aterminal and a multi-line gateway in a cordless telephony environmentAccording to the present invention, multiple logical channels areestablished and used as signaling resources for calls on the multiplelines, and also for data transfers between the gateway and terminal.Utilizing the techniques described herein, a terminal can handlemultiple calls on different lines and at the same time access datastored at the gateway.

According to a first aspect of the present invention, a plurality oflogical channels are established over an asynchronous channel between aterminal and a gateway. These logical channels are assigned to callsthat are set-up between the terminal and gateway. When used as asignaling resource, the logical channels allow the terminal todistinguish between signaling information for multiple simultaneouscalls. The calls are associated with another speech or data channel thatwill bear the voice signal, referred to herein as a bearer channel. Aseach new call is set-up, an existing bearer channel can be used, or anew bearer channel can be created to carry the call. Synchronouspoint-to-point links can be used as bearer channels. Logical channelscan also be used as bearer channels, where the voice signal istransmitted as packets of data according to “voice over IP” (VoIP)techniques.

According to a second aspect of the present invention, a logical channelis also established over an asynchronous channel to handle datatransfers between the gateway and terminal. Using this logical channel,the terminal can access data stored at the gateway without disruptingany ongoing calls.

These and other aspects of the present invention will become apparentfrom the following drawings and description.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described with reference to the accompanyingdrawings. In the drawings, like reference numbers indicate identical orfunctionally similar elements. Additionally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

FIG. 1 depicts an example cordless telephony environment within whichvarious example embodiments of the present invention operate.

FIG. 2 depicts a flowchart that describes at a high level the operationof a gateway and one or more terminals within the cordless telephonyenvironment according to an example embodiment of the present invention.

FIG. 3 depicts a gateway and an example terminal device in greaterdetail according to an example embodiment of the present invention.

FIG. 4 depicts the operation of establishing an ACL link and one or morelogical channels in greater detail according to an example embodiment ofthe present invention.

FIG. 5 depicts the operation of carrying out a call according to anexample embodiment of the present invention.

FIG. 6 depicts an example association between calls, logical channels,and bearer channels according to an example embodiment of the presentinvention.

DETAILED DESCRIPTION

The present invention provides a system and method for simultaneouslyhandling calls on multiple lines and for transferring data between aterminal and a multi-line gateway in a cordless telephony environment.Generally speaking, according to the present invention multiple logicalchannels are established and used as signaling resources for calls onthe multiple lines. Logical channels are also used for data transfersbetween the gateway and terminal. Utilizing the techniques describedherein, a terminal can handle simultaneous calls on multiple lines andat the same time transfer data between the gateway and terminal.

Example embodiments of the present invention in many instances aredescribed herein in the context of an example BT cordless telephonyenvironment. These techniques are applied to the BT environment forillustrative purposes only, and should not be construed as limited tothis environment. Rather, it will be apparent to those of skill in therelevant art that the principles described herein can also be applied toother similar cordless telephony environments.

As will be apparent to those skilled in the art, the present inventioncan include one or more computer programs which cause wireless devicesto perform the functions described herein and illustrated in theappended flowcharts. However, it should also be apparent that therecould be many different ways of implementing the invention in computerprogramming, or a combination of hardware and software, and theinvention should not be construed as limited to any one set of computerprogram instructions. Further, a skilled programmer would be able towrite such a computer program to implement the disclosed inventionwithout difficulty based on the flowcharts and associated writtendescription included herein. Therefore, disclosure of a particular setof program code instructions is not considered necessary for an adequateunderstanding of how to make and use the invention.

FIG. 1 depicts an example cordless telephony environment 100 withinwhich various example embodiments of the present invention operate. Agateway 102 communicates with one or more terminal devices 104 (shown as104A and 104B). Wireless links 110 (shown as 110A and 110B) areestablished between gateway 102 and each of the terminal devices 104.Gateway 102 and terminal devices 104 together form a wireless network130. In the example BT environment, wireless links 110 representshort-range RF links wherein the gateway and terminal devicescommunicate according to the protocols described in the BTspecification. Further, wireless network 130 represents a piconet.

Gateway 102 is also connected to an external network 106 via one or morelines 108, where the number of lines is given by N. External network 106can represent any network capable of carrying telephony information,such as a public switched telephone network (PSTN), the Internet andother wide area networks (WANs), cellular networks (terrestrial andsatellite) such as the Global System for Mobile communications (GSM)networks, and various combinations of the above. Lines 108 represent thecommunication path over which telephony information travels betweenexternal network 106 and gateway 102. For example, lines 108 canrepresent land lines such as a standard 3-wire telephone line, anIntegrated Services Digital Network (ISDN) line, or a high-speedconnection to the Internet such as T1 or T3 lines. Lines 108 can alsorepresent wireless connections, such as a terrestrial or satellitecellular connection. As used herein, each line 108 can carry a singlecall at any given time, though multiple calls can take placesimultaneously on different lines 108.

Gateway 102 acts as a terminal endpoint from the point of view ofnetwork 106 and handles all interactions with network 106. Gateway 102is the central point with respect to external calls, which means that ithandles all call set-up requests to/from network 106. Gateway 102 canrepresent, for example, a PSTN home base station, an ISDN home basestation, a GSM gateway, a satellite gateway and an H.323 (standard fortransferring multimedia videoconferencing data over packet-switchednetworks, such as TCP/IP) gateway.

Terminal devices 104 represent wireless user terminals, such as acordless telephone, a dual-mode cellular/cordless phone (e.g., a 3-in-1phone) or a personal computer (PC). In general, terminal devices 104 canrepresent any electronic device that is equipped with a wirelesstransceiver, such as the Bluetooth™ Module (part number ROK 101 007)produced by Ericsson. Terminal devices 104 can, for example, represent awide range of consumer electronic devices such as a laptop computer,PDA, cordless telephone, stereo equipment, television or VCR. Terminaldevices 104 can represent identically or similarly configured devices,such as multiple cordless telephones used in conjunction with a singlebase station (gateway 102). Alternatively, terminal devices 104 canrepresent dissimilar devices, so long as each device is capable ofcommunicating over wireless link 110 according to the techniquesdescribed herein.

In the example BT environment, gateway 102 and terminal devices 104operate in conformance with the Telephony Control protocolSpecification—Binary (TCS) portion of the BT specification as well asthe CTP. The TCS protocol defines call control signaling for theestablishment of speech and data calls between BT devices. The TCSprotocol also defines mobility management procedures for handling BT TCSdevices. The techniques described herein according to various exampleembodiments of the present invention in many cases extend the TCS andCTP protocols to provide additional functionality without violating theterms of the protocol.

Terminal devices 104 establish wireless links 110 upon coming withinrange of gateway 102. In the example BT environment described in theCTP, terminal devices 104 that are out of range of gateway 102 searchfor it by periodically trying to page the device address of the gateway.Gateway 102 devotes much of its free capacity (considering powerlimitations and ongoing signaling) to page scanning in order to allowroaming terminal devices 104 that enter the range of gateway 102 to findthe gateway as quickly as possible. When terminal device 104 hassuccessfully paged gateway 102 (making terminal device 104 temporarilythe master), a master-slave switch is performed according to the BTspecification so that gateway 102 becomes the piconet master. As master,gateway 102 controls the power mode of terminal devices 104 and maybroadcast information to terminal devices 104.

The TCS and CTP protocols provide for the handling of calls on a singleline 108. These protocols do not, however, describe how to handlesimultaneous calls on multiple lines. Nor do these protocols describehow to transfer data between gateway 102 and terminal devices 104.Various example embodiments of the present invention will now bedescribed for handling calls and data transfers for multi-line gateway102.

FIG. 2 depicts a flowchart 200 that describes at a high level theoperation of gateway 102 and terminals 104 according to an exampleembodiment of the present invention. In operation 202, an asynchronouslink is established between gateway 102 and terminal device 104, such asan ACL link in the example BT environment. The bandwidth associated withthe ACL link is divided amongst logical channels that are multiplexedover the ACL link. One or more of these logical channels are establishedin operation 202.

According to an example embodiment of the present invention, operation202 is performed when a terminal device 104 enters the range of gateway102. By establishing the ACL link and logical channels at the outset,these resources are already available when needed to handle a call,thereby reducing the call set-up time. However, it will be apparent tothose skilled in the art that the ACL link and logical channels couldalternatively be established at a later time.

Operations 204 through 210 describe the behavior of gateway 102 andterminal devices 104 once the initial ACL link and logical channels havebeen established. As shown in operations 204 and 208, terminal devices104 and gateway 102 wait for either a call set-up request or a datatransfer request.

In operation 204, calls are set-up upon the arrival of an incoming callfor one of the terminal devices 104, or when a terminal device 104 wantsto make an outgoing call. If either of these events occurs, then inoperation 206 the call is carried out. Each call must have associatedwith it a signaling channel and a bearer channel. TCS signalinginformation is exchanged over the signaling channel, whereas the voicesignal is carried on the bearer channel. According to the presentinvention, the logical channels established in operation 202 aredynamically assigned to calls as they are set-up, where the logicalchannel acts as the signaling channel for the call. All of the signalinginformation for a particular call is therefore transmitted betweengateway 102 and terminal device 104 over the assigned logical channel.The call is also associated with a bearer channel to carry the voicesignal. An existing bearer channel can be used, or a new bearer channelmight be created. Further, two or more calls can share a single bearerchannel.

According to the present invention, terminal device 104 is able todistinguish the signaling information for simultaneous calls because thesignaling information associated with each call is transmitted over adistinct logical channel. Packets transmitted over the ACL link via aparticular logical channel are associated with the call to which thelogical channel is assigned. Terminal device 104 can thereforedifferentiate between the signaling information associated with multiplesimultaneous calls. As described in further detail below, this allowsterminal device 104 to simultaneously handle calls on multiple lines108.

In operation 208, if either gateway 102 or terminal device 104 request adata transfer from one device to the other, then in operation 210 therequested transfer is carried out. According to the present invention, alogical channel for handling these data transfers is established inoperation 202. The data is transferred as packets assigned to thelogical channel over the ACL link. The data transfer does not interferewith the handling of calls because different logical channels are usedfor the data transfer and for call signaling. Data can therefore beexchanged between gateway 102 and terminal device 104 while at the sametime handling simultaneous calls on multiple lines 108.

The operations depicted in FIG. 2 are described in greater detail belowaccording to various example embodiments of the present invention. Theseoperations will be described in conjunction with FIG. 3, which depictsgateway 102 and an example terminal device 104 in greater detailaccording to an example embodiment of the present invention. As shown inFIG. 3, gateway 102 and terminal device 104 both include a TCS layer 310(shown as 310A and 310B, respectively), an RF communications protocol(RFCOMM) 320 (shown as 320A and 320B, respectively), a Logical LinkControl and Adaptation Protocol (L2CAP) layer 330 (shown as 330A and330B, respectively), and a SCO management module 340 (shown as 340A and340B, respectively). These components are described in greater detailbelow.

Terminal device 104 also includes a terminal application 350. Terminalapplication 350 represents the software that controls the operation ofthe other components within terminal device 104, manipulates the dataexchanged over wireless link 110, and other necessary functions thatwould be apparent to those skilled in the art. These interactions withTCS 310B, RFCOMM 320B, and SCO management module 340B are depicted aslines 352A, 352B, and 352C respectively. Lines 352A represent controlinformation and data flowing from terminal application 350 to the othercomponents, and data flowing in the opposite direction.

FIG. 4 depicts the operation of establishing an ACL link and logicalchannels (operation 202) in greater detail according to an exampleembodiment of the present invention. In operation 402, an ACL link 302is established between gateway 102 and terminal device 104. As describedabove, ACL link 302 can be established upon terminal 104 coming withinrange of gateway 102. ACL link 302 provides a packet-switched connectionbetween gateway 102 and all of the terminal devices 104 within piconet130. According to the BT specification, only a single ACL link can existbetween a given master and slave. In the cordless telephony environment,only one ACL link 302 can exist between gateway 102 (the piconet master)and each terminal device 104 (the piconet slaves).

In operation 404, an L2CAP channel 316 is established for each line 108connecting gateway 102 and external network 106. As described in the BTspecification, L2CAP layer 330 provides for the creation of logicalchannels that are used for all TCS control signaling. L2CAP channels 316can be either connection-oriented or connectionless. Connection-orientedL2CAP channels are for point-to-point signaling between two devices,whereas connectionless L2CAP channels are for point-to-multipointbroadcast signaling from the master to all slave devices. L2CAP channels316 as used herein refer to connection-oriented channels unlessindicated otherwise.

Each one of the end-points of an L2CAP channel 316 is referred to by achannel identifier (CID). CIDs are local names representing a logicalchannel end-point on the device. As shown in FIG. 3, L2CAP channels 316have CIDs on the gateway side given by CH-ID G_(A) through CH-ID G_(N),and on the terminal-side given by CH-ID T_(A) through CH-ID T_(N).

According to the CTP, terminal device 104 establishes a single L2CAPchannel 316 to be used for all TCS signaling. However, having only asingle L2CAP channel 316 does not allow terminal 104 to handle multiplecalls because terminal 104 has no way to associate signaling informationreceived via the channel with a particular call. According to thepresent invention, multiple L2CAP channels 316 are established to beused for TCS signaling, where each call is assigned its own L2CAPchannel 316. So, in operation 404, terminal device 104 establishesmultiple L2CAP channels 316 that are assigned CIDs selected from thepool of available CIDs.

According to a first example embodiment of the present invention, anL2CAP channel 316 is established for each line 108 connecting gateway102 and network 106. Sufficient signaling resources are therefore alwaysavailable, even if a call is being handled simultaneously on every line108. This example embodiment is depicted in FIGS. 3 and 4, wherein acall 312 (shown as call 1 through call N) on each line 108 is assignedits own L2CAP channel 316. Call 312 can represent an incoming oroutgoing call between terminal device 104 and network 106. Call 312 canalso represent an intercom call between gateway 102 and terminal device104.

However, according to other example embodiments of the presentinvention, the number of L2CAP channels 316 established in operation 404need not equal the number of lines 108. Fewer L2CAP channels 316 mightbe established if, for example, resources are to be conserved.Conversely, additional L2CAP channels 316 might be established, forexample, to support an intercom call between gateway 102 and terminal104.

In operation 406, another L2CAP channel 324 is established fortransferring data between terminal 104 and gateway 102. In the exampledepicted in FIG. 3, a data exchange application 326 represents softwarethat stores the data in gateway 102 that is of interest to terminaldevice 104, and causes the data to be transferred upon request toterminal 104. This data transfer from data exchange application 326 toterminal application 350 occurs via L2CAP channel 324 having agateway-side CID shown as CH-ID G_(Z) and a terminal-side CID shown asCH-ID T_(Z).

According to an example embodiment of the present invention, L2CAPchannel 324 is established once terminal device 104 comes within rangeof gateway 102 along with the other L2CAP channels. L2CAP 324 channel istherefore ready in the event that a data transfer is initiated. However,according to other example embodiments of the present invention, L2CAPchannel 324 may not be established until it is needed. Alternatively,L2CAP channel 324 may not be established at all if such data transfersare not supported by the particular application.

As shown in FIG. 3, L2CAP 330 performs protocol multiplexing accordingto the particular Protocol/Service Multiplexor (PSM) assigned to a givenL2CAP channel. The PSM value identifies the particular protocol withwhich an L2CAP channel is associated. For example, all L2CAP channels316 have a PSM equal to TCS-BIN-CORDLESS and are therefore routed to TCS310. L2CAP channel 324 has an PSM equal to APP-SPECIFIC-PSM and isrouted to data exchange application 326.

Returning now to FIG. 2, ACL link 302, L2CAP channels 316, and L2CAPchannel 324 (if desired) are established in operation 202. As describedabove, when incoming or outgoing calls 312 are set-up on a line 108, thecall is carried out in operation 206. FIG. 5 depicts this operation ingreater detail according to an example embodiment of the presentinvention. In operation 502, an available L2CAP channel 316 is assignedto the call 312. The assigned L2CAP channel 316 will carry all TCS callsignaling associated with the call 312. For example, in FIG. 3, call Iis assigned the L2CAP channel 316 having a CID of CH-ID G_(A). Terminal104 therefore knows that all TCS signaling information received overL2CAP channel 316 having a CID of CH-ID T_(A) is associated with call 1.

According to an example embodiment of the present invention, theassignment of L2CAP channels 316 to calls 312 is done dynamically as thecalls appear on lines 108. Once the L2CAP channels 316 are establishedin operation 202, they remain unassigned until the first call 312 is setup, at which point one of the L2CAP channels is assigned to the call.The L2CAP channel 316 is then released when the call 312 is completed.In this manner, L2CAP channels 316 act as signaling resources for calls312 that are assigned dynamically as needed. Dynamic assignment isparticularly applicable to those example embodiments wherein there arefewer L2CAP channels 316 than there are lines 108. In these exampleembodiments, calls 312 cannot be set up until an L2CAP channel 316becomes available. However, according to other example embodiments ofthe present invention, L2CAP channels 316 may be assigned in a staticfashion.

In operation 504, a determination is made whether to use an existingbearer channel, or to establish a new bearer channel for the call. If anexisting bearer channel is available, in operation 506 the call isassociated with the available bearer channel and the call proceeds underthe control of the assigned L2CAP signaling channel 316. Otherwise a newbearer channel is established in operation 508 and associated with thecall so that the call can proceed under the control of the assignedL2CAP signaling channel 316. In some situations, examples of which aredescribed below, multiple calls 312 can share the same bearer channel.

Different types of channels can be used as bearer channels of the voicesignal associated with a call. Two types are described herein: SCO linksand L2CAP channels carrying VoIP data. As described above, SCO links arepoint-to-point links between a master and a slave that support real-timevoice traffic. SCO links are therefore often used as bearer channels. Asshown in FIG. 3, SCO management module 340 can include one or more voicebearers 342 associated with SCO links 304. The maximum number of SCOlinks 304 (shown as M in FIG. 3) may be limited by the communicationprotocol. According to the current version of the BT specification, amaster device can support up to three SCO links to the same slave or todifferent slaves. A slave device can support up to three SCO links fromthe same master, or two SCO links if the links originate from differentmasters.

L2CAP channels can also be used as bearer channels for calls 312 usingVoIP techniques. As shown in FIG. 3, one or more VoIP bearers 322 can beestablished within RFCOMM 320 for exchanging VoIP data over an L2CAPbearer channel 328. RFCOMM 320 represents a protocol that providesemulation of serial ports over L2CAP 330. RFCOMM 320 utilizes a VoIPapplication (not shown) to generate the VoIP packetized data from thevoice signal associated with a call. The L2CAP bearer channels 328 canbe established at the same time the other L2CAP signaling channels areestablished. Alternatively, L2CAP bearer channels 328 can be created asneeded. VoIP bearers 322 can be used, for example, if a call 312 needsto be set up and the maximum number of SCO links 304 has been reached.

Both SCO bearers 342 and VoIP bearers 322 operate under the control ofthe TCS signaling on the L2CAP channel 316 assigned to the call 312.This control relationship is depicted as control path 318 in FIG. 3,connecting calls 312 to VoIP bearers 322 and voice bearers 342.

According to the present invention, a flexible framework is employedwherein different types of bearer channels can be freely associated withdifferent calls. FIG. 6 depicts an example association of calls 312,VoIP bearers 322, and voice bearers 342. As shown in FIG. 6, forexample, the voice signal for call 3 is assigned to voice bearer 1.Voice bearer 1 therefore operates under the control of the TCS signalingon the L2CAP channel having a channel ID of CH-ID G_(C) on the gatewayside and CH-ID T_(C) on the terminal side. This control relationship isdepicted as control path 318B. Similarly, the voice signal for call 4can be assigned to a VoIP bearer that operates under the control of theL2CAP channel having a channel ID of CH-ID G_(D) on the gateway side andCH-ID T_(D) on the terminal side. The architecture therefore supportsthe concurrent use of different types of bearer channels.

Multiple calls 312 can also be associated with the same bearer channel.For example, when a first call is put on hold, a second call can use thebearer channel assigned to the first call. Also, certain applicationsmay support conference calling where the voice signals from severalcalls share a common bearer channel. As shown in FIG. 6, for example,calls 1 and 2 share voice bearer 2. Voice bearer 2 therefore operatesunder the shared control of the TCS signaling on the L2CAP channelsassociated with calls 1 and 2.

Returning now to FIG. 2, if data transfers are initiated in operation208, the data transfer is carried out in operation 210. Data transferscan be initiated in various ways such as, for example, by user requestat terminal device 104. Data transfers might also be initiatedautomatically to insure that terminal device 104 is periodicallyrefreshed with the latest stored data 326. As described above, data istransferred between gateway 102 and terminal device 104 using L2CAPchannel 324.

Gateway 102 and terminals 104 are configured to be interoperable withconventional devices whose operation does not extend beyond the CTPprotocol. For example, when a conventional CTP terminal device comes incontact with gateway 102 configured according to the present invention,gateway 102 sets up a single L2CAP channel 316 and carries out only onecall at a time. Gateway 102 can allocate any available line 108 whenterminal device 104 requests an outgoing call. Further, gateway 102 canhandle calls 312 on multiple lines 108, but only so long as the calls donot occur simultaneously. However, gateway 102 cannot perform datatransfers with a conventional CTP terminal device.

As another example, when a terminal device 104 configured according tothe present invention comes in contact with a conventional single-linegateway, the terminal's requests to establish multiple L2CAP channels316 will likely fail. Terminal device 104 can infer from this failurethat the gateway does not support multiple lines. Similarly, a requestfrom terminal device 104 to establish an L2CAP channel 324 for datatransfers will also likely fail, causing the terminal to infer that thegateway does not support the data transfer feature.

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample only, and not limitation. Thus, the breadth and scope of thepresent invention should not be limited by any of the above-describedexemplary embodiments, but should be defined only in accordance with thefollowing claims and their equivalents.

The previous description of the preferred embodiments is provided toenable any person skilled in the art to make or use the presentinvention. While the invention has been particularly shown and describedwith reference to preferred embodiments thereof, it will be understoodby those skilled in the art that various changes in form and details maybe made therein without departing from the spirit and scope of theinvention.

1. A method comprising: (a) establishing a plurality of logical channelsbetween a terminal and a gateway, wherein each logical channel comprisesa channel identifier that represents a logical channel end point; and(b) associating a first logical channel of the plurality of logicalchannels with a first bearer channel that carries a first call, whereinall and only signaling information for the first call is configured tobe transmitted over the first logical channel, and wherein a first voicesignal is configured to be carried over the first bearer channel; and(c) associating a second logical channel of the plurality of logicalchannels with a second bearer channel that carries a second call,wherein all and only signaling information for the second call isconfigured to be transmitted over the second logical channel, andwherein a second voice signal is configured to be carried over thesecond bearer channel, wherein one of the first or second bearerchannels includes a synchronous channel.
 2. The method of claim 1,wherein the method further comprises: (d) associating a third logicalchannel of the plurality of logical channels with an asynchronouschannel that accesses data from said gateway.
 3. The method of claim 1,wherein one of the first or second bearer channels includes anasynchronous channel.
 4. The method of claim 1, wherein one or both ofthe first and/or second bearer channels carries voice over IP (VoIP)data.
 5. The method of claim 1, wherein said gateway is coupled to anetwork via a plurality of lines, and wherein said first call is carriedon one of said plurality of lines.
 6. The method of claim 5, whereinsaid network comprises a public switched telephone network (PSTN).
 7. Asystem comprising: a terminal for establishing a plurality of logicalchannels, wherein each logical channel comprises a channel identifierthat represents a logical channel end point; and a gateway, coupled tosaid plurality of logical channels, dynamically assigning at least twological channels in said plurality of logical channels to calls as thecalls are set up between said gateway and said terminal, wherein one orboth of said terminal or said gateway associates a first logical channelof the plurality of logical channels with a first bearer channel thatcarries a first call, wherein all and only signaling information for thefirst call is configured to be transmitted over the first logicalchannel, and wherein a first voice signal is configured to be carriedover the first bearer channel, wherein one or both of said terminal orsaid gateway associates a second logical channel of the plurality oflogical channels with a second bearer channel that carries a secondcall, wherein all and only signaling information for the second call isconfigured to be transmitted over the second logical channel, andwherein a second voice signal is configured to be carried over thesecond bearer channel, wherein one of the first or second bearerchannels includes a synchronous channel.
 8. The system of claim 7,wherein said gateway is coupled to a network via a plurality of lines.9. The system of claim 7, wherein said gateway further associatesanother logical channel with an asynchronous channel that accesses datafrom said gateway.
 10. The system of claim 7, wherein at least one ofthe bearer channels includes an asynchronous channel.
 11. The system ofclaim 7, wherein at least one of the bearer channels carries voice overIP (VOIP) data.
 12. At least one non-transitory computer readable mediahaving stored thereon code for supporting communication between agateway and a terminal, the code operable to cause performance of theoperations comprising: (a) establishing a plurality of logical channelsbetween a terminal and a gateway, wherein each logical channel comprisesa channel identifier that represents a logical channel end point;. (b)dynamically assigning and associating a first logical channel of theplurality of logical channels with a first bearer channel that carries afirst call as the first call is set up, wherein all and only signalinginformation for the first call is configured to be transmitted over thefirst logical channel, and wherein a first voice signal is configured tobe carried over the first bearer channel; and (c) dynamically assigningand associating a second logical channel of the plurality of logicalchannels with a second bearer channel that carries a second call as thesecond call is set up, wherein all and only signaling information forthe second call is configured to be transmitted over the second logicalchannel, and wherein a second voice signal is configured to be carriedover the second bearer channel, wherein one of the first or secondbearer channel includes a synchronous channel.
 13. A system comprising:an integrated circuit for use in a terminal, said terminal forestablishing a plurality of logical channels, wherein each logicalchannel comprises a channel identifier that represents a logical channelend point, and wherein said terminal communicates with a gateway, saidgateway configured to dynamically assign at least two logical channelsin said plurality of logical channels to calls as the calls are set upbetween said gateway and said terminal, wherein one or both of saidterminal or said gateway associates a first logical channel of theplurality of logical channels with a first bearer channel that carries afirst call, wherein all and only signaling information for the firstcall is configured to be transmitted over the first logical channel, andwherein a first voice signal is configured to be carried over the firstbearer channel, wherein one or both of said terminal or said gatewayassociates a second logical channel of the plurality of logical channelswith a second bearer channel that carries a second call, wherein all andonly signaling information for the second call is configured to betransmitted over the second logical channel, and wherein a second voicesignal is configured to be carried over the second bearer channel,wherein one of the first or second bearer channels includes asynchronous channel.
 14. The system of claim 13, wherein said gateway iscoupled to a network via a plurality of lines.
 15. The system of claim13, wherein said gateway further associates another logical channel withan asynchronous channel that accesses data from said gateway.
 16. Thesystem of claim 13, wherein at least one of the bearer channels includesan asynchronous channel.
 17. The system of claim 13, wherein at leastone of the bearer channels carries voice over IP (VoIP) data.